-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No schema files #159 #371
No schema files #159 #371
Conversation
Signed-off-by: Paul Bastide <pbastide@us.ibm.com>
fhir-persistence-schema/src/main/java/com/ibm/fhir/schema/app/SimpleSchemaPrinter.java
Outdated
Show resolved
Hide resolved
fhir-persistence-schema/src/main/java/com/ibm/fhir/schema/app/SimpleSchemaPrinter.java
Outdated
Show resolved
Hide resolved
fhir-persistence-schema/src/main/java/com/ibm/fhir/schema/app/SimpleSchemaPrinter.java
Outdated
Show resolved
Hide resolved
fhir-persistence-schema/src/main/java/com/ibm/fhir/schema/app/SimpleSchemaPrinter.java
Outdated
Show resolved
Hide resolved
* The following classes are 'dummy implementations' that enable printing of the | ||
* SQL. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why do we need the dummy stubs? no way to just use the existing Print classes?
if its really needed, maybe we introduce test dependency for creating the stubs from the Interface?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
existing print classes miss many commands and do not fully include all the commands
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we fix those?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not really. It'll be a pain to re-engineer to support it; I looked at it. This is the reliable way - regardless of IDatabaseTarget and IDatabaseTranslator.
do we really want to commit to keeping the DDL up-to-date in our docs? |
Perfectly valid question... maybe teach questions/decision? |
Signed-off-by: Paul Bastide <pbastide@us.ibm.com>
Signed-off-by: Paul Bastide <pbastide@us.ibm.com> Co-Authored-By: Lee Surprenant <lmsurpre@us.ibm.com>
Signed-off-by: Paul Bastide <pbastide@us.ibm.com> Co-Authored-By: Lee Surprenant <lmsurpre@us.ibm.com>
Signed-off-by: Paul Bastide <pbastide@us.ibm.com> Co-Authored-By: Lee Surprenant <lmsurpre@us.ibm.com>
got it |
Signed-off-by: Paul Bastide <pbastide@us.ibm.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Signed-off-by: Paul Bastide pbastide@us.ibm.com